wayfinder #345: engagement northstar — l1-fieldwork-1 registered - #357
Merged
Conversation
Rulings (operator, 2026-08-01, grilled this session): - slug l1-fieldwork-1, engagement-scoped ordinal; repo (app) = fieldwork-1, private; retires at sustainment/exit, engagement #2 mints l1-fieldwork-2 - 5 properties: arc traversed / value in the customer's numbers / dossier G1-G6 / playbook shadow / mechanized-auditable delivery (P5 = the operator's NASA-SEH elevation, applied recursively to self-built components — refines, does not reverse, the no-literal-ISO-15288 charting ruling) - standard movement contract: operator-asserted currents; slices ship 'Movement proposal:' lines only; record-movement appends from merged PRs - numerics PROPOSED (capture-agent precedent), operator calibrates - northstar FILE lands with the repo bootstrap (#349) in the private repo; registry carries slug/path/anonymous comment only (client-data ruling); absent-checkout = shadow WARN until #349 (verified: lint 0 errors) - map re-anchor to ns:l1-fieldwork-1 ruled yes, executes at #349 - fog graduated: seh tie-in -> P5 + widened #350; re-anchor -> ruled - new task ticket #356 (public-map client-intel sanitization) wired as #344 child Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Contributor
Skill Audit — PR #357Skills used during development
Recommended skills (based on diff analysis)
Coverage
Generated by skill-audit |
This was referenced Aug 1, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Resolves the Engagement northstar ticket (#345) of the texas-rr-engagement map (#344). Grilling ran this session (AskUserQuestion, 6 operator rulings, 2026-08-01).
Rulings
l1-fieldwork-1— engagement-scoped, purpose-named, ordinal. Repo (app) =fieldwork-1, private. Retires at sustainment/exit; engagement feat: migrate all commands to skill directories #2 mintsl1-fieldwork-2.Movement proposal: ns:l1-fieldwork-1#Pn N% -> M% — evidence: …lines;record-movement.mjsappends from merged PRs; a slice that cannot name its property does not dispatch.ns:l1-fieldwork-1at Engagement repo bootstrap (private; proof-plan skeleton; fleet-onboard) #349, when the anchor resolves.Changes
decisions/northstar/README.md— registry entry (20th), client-anonymous, absent-checkout note.decisions/wayfinder/texas-rr-engagement.md— Engagement northstar: naming, properties, movement contract #345 closed into Decisions so far; two fog items graduated (seh tie-in → P5 + widened Engagement stage-gates + TPM discipline #350; re-anchor → ruled); post-Engagement northstar: naming, properties, movement contract #345 frontier; Public-map client-intel sanitization #356 row.Lint
northstar-lint --check: 0 errors, 3 WARNs —l1-fieldwork-1absent-checkout vantage WARN (expected; closes at #349) + 2 pre-existing rollup drifts.No roadmap entry yet — the delivery roadmap is minted at map handoff (slice refinery).
🤖 Generated with Claude Code